Techniques for establishing a communication handoff threshold using user feedback

ABSTRACT

Examples are disclosed for user feedback to enable a handoff profile for a dual-mode hybrid mobile device. In some examples communication link handoff logic may be executed by the processor component to receive user feedback during a test voice call mediated with a call server, the user feedback pertaining to one or more Voice-over Internet Protocol (VoIP) communication link parameters for the communication link between the hybrid mobile device and the call server. The communication link parameters are correlated with a call quality threshold based on the user feedback and a handoff profile is established for the hybrid mobile device based on the call quality thresholds, the handoff profile operative to establish criteria for switching the VoIP communication link to a communication link over a different network.

TECHNICAL FIELD

Examples described herein are generally related to techniques forestablishing a handoff profile for a dual network communication deviceusing user feedback.

BACKGROUND

Mobile telephony devices utilizing wireless communication protocols areubiquitous. Many of these devices utilize one of the competing cellularnetworks (e.g., GSM or CDMA) to place and receive telephone calls toother telephony endpoint devices. A telephony endpoint device mayinclude another mobile telephony device on the same or another cellularnetwork, a Voice-over-IP (VoIP) telephony device, and/or a plain oldtelephone service (POTS) telephony device. Each of these telephonyendpoint devices may use a different access network but all areinterfaced at some point to allow for communication among the differentnetworks.

Recently, there has been introduced another type of mobile telephonydevice, one that is capable of utilizing multiple different networksdepending on the current location or network conditions pertaining tothe mobile telephony device. Such a mobile telephony device may becharacterized as a hybrid mobile device due to its capability of makingand receiving telephone calls on at least two distinct networks. Somehybrid mobile devices include the ability to start or establish atelephone call on one network (e.g., an IP based VoIP network over awireless fidelity (WiFi) connection) and handoff the call to a secondnetwork (e.g., a cellular network) when conditions on the originalnetwork degrade. Such a handoff may occur, for instance, when the mobilehybrid device moves out of range of the IP based WiFi access point.Rather than dropping the call, the hybrid mobile device, in conjunctionwith the a network based server, may switch to a cellular connectionprior to severing the WiFi VoIP connection thereby ensuring that thehybrid mobile device stays connected to the other telephony endpoint andthe call is not dropped.

Determining when to initiate the handoff to avoid dropping a call canvary based on a number of factors, including but not limited to networkconditions, signal strength, location and the like and is typically setbased on manufacturer or carrier default settings. Incorporating userfeedback with respect to actual call quality and network conditions intothis determination may improve the user experience and the device andnetwork performance. As such, described herein are methods, systems, andtechniques for establishing a handoff profile based on variouscommunication link parameters using user feedback.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example block diagram for a networked environment.

FIG. 2 illustrates an example block diagram for a call server.

FIG. 3 illustrates an example block diagram for a hybrid mobile device.

FIG. 4 illustrates an example block diagram for a communication sessionhandoff.

FIG. 5A illustrates an example of a first operating environment.

FIG. 5B illustrates an example of a second operating environment.

FIG. 6A illustrates an example of a first logic flow.

FIG. 6B illustrates an example of a second logic flow.

FIG. 6C illustrates an example of a third logic flow.

FIG. 6D illustrates an example of a fourth logic flow.

FIG. 6E illustrates an example of a fifth logic flow.

FIG. 7 illustrates an example of a storage medium.

FIG. 8 illustrates an example of a device.

DETAILED DESCRIPTION

The embodiments described herein disclose systems and methods forintelligently incorporating user feedback to establish a handoff profilebased on various communication link parameters to enhance communicationsessions between or among communication devices. The systems and methodsof the invention may be embodied in and performed by communicationdevices, call servers and other devices, and software instructionsexecuted by some or all of such devices, as will be explained in detailbelow. The different types of networks contemplated herein include, forexample, cellular mobile networks, the public switched telephone network(PSTN), and data networks, such as the Internet or other IP-basednetworks, including wide area networks, local area networks, andcombinations thereof.

As used herein the term “communication session” is meant to generallyindicate any one-way or two-way exchange of information between two ormore communication devices. Communication sessions may include voice,data, video, and multimedia communication sessions, or any other type ofdata communication sessions or messaging exchanges. As used herein, theterm “communication link” is intended to mean a physical or logicalchannel that connects two or more devices. A communication link may be asignaling link or a media link. In this context, a communication sessionmay be established via one or more communication links. One or moremedia streams may be transmitted over a communication link. A callserver may be situated between communication devices thereby making thecall server an endpoint in a communication link. The call server may behosted within an IP network such as, for instance, the Internet or aLAN/WAN accessible to the Internet.

The convergence of and inter-operation among different types of networktechnologies (e.g., heterogeneous network inter-operability) blurs theline between various distinct networks. This disclosure discusses accessnetworks that may be characterized as the portion of a communicationnetwork that connects subscriber communication devices to a serviceprovider's core network. An access network may also be referred to asthe interface between the communication device and the network. Anothertype of interface may be the interface between networks. That is, theinterface necessary to facilitate seamless communication from onenetwork to another.

Therefore, references herein to a communication device capable ofconnecting to or communicating via a mobile carrier network refer to acommunication device equipped with a cellular transceiver for wirelesscommunication with base stations and other mobile carrier network accesspoints. Similarly, references herein to a communication device capableof connecting to or communicating via a data network refer to acommunication device equipped with a transceiver or other networkinterface for wireless communication (e.g., 802.11) with a router orother data network access point. One particular communication device maybe characterized herein as a wireless handset. A wireless handset mayinclude multiple RF transceivers, one of which may be operable toconnect to an access network for a mobile carrier network (e.g.,cellular network) and another of which may be operable to connect to anaccess network for an IP data network (e.g., 802.11).

FIG. 1 illustrates an exemplary networked environment 100 forimplementing certain exemplary embodiments described herein. Thenetworked environment 100 may include multiple distinct inter-connectednetworks such as, for instance, a large scale internet protocol (IP)network (e.g., the Internet) 101, one or more IP based local areanetworks or wide area networks (LAN/WAN) 122, mobile carrier networks110, and the PSTN 108. While these distinct networks utilize differentprotocols and signaling schemes, there are various interfaces that allowfor the seamless transition of voice and data (including text, audio,and video) such that various communication endpoints may communicatewith one another over one or more of these inter-connected networks.

The PSTN 108 can be characterized as a circuit switched point-to-pointcommunication network in which a physical connection between theendpoints is maintained for the duration of the connection. The PSTN 108may also be referred to as the legacy telephone network as it is thebackbone infrastructure for connecting endpoints comprised of Plain OldTelephone Service (POTS) phones 116.

Mobile carrier networks 110 (sometimes referred to as cellular networks)may come in different varieties based on the radio transmission scheme125 between a communication device known as a wireless handset (e.g.,mobile or cellular phone) 114 and the mobile carrier network basestation 112 that is in communication with the wireless handset 114. Twosuch radio transmission schemes are the Global System for MobileCommunication (GSM) and Code Division Multiple Access (CDMA). Theseradio transmission schemes are incompatible with one anothernecessitating an intervening interface to allow communication betweenendpoints on either network. In addition, each network may operate overa specific frequency ranges. Often, there may even be an interveningnetwork such as the PSTN 108 between two distinct mobile carriernetworks 110. Each mobile carrier network 110 includes an interface tothe PSTN 108 such that calls crossing that interface can be handled bythe receiving network whether it is a mobile carrier network 110 or thePSTN 108.

Various mobile carrier network operators base their network on one ofthe radio transmission schemes 125 and provide service to wirelesshandsets 114 using that radio transmission scheme 125 over a definedfrequency band. For example, a wireless handset 114 wirelesslycommunicates with a base station 112 that serves as an access network tothe mobile carrier network 110. The base station 112 authenticates andauthorizes the wireless handset 114 to the mobile carrier network 110and, in conjunction with other equipment within the mobile carriernetwork 110, manages calls to and from the wireless handset 114. Themobile carrier network 110 provides connectivity for any wirelesshandsets 114 capable of cellular transmission that are physicallylocated within range of the mobile carrier network 110. The range of amobile carrier network 110 depends in part on an amplification, power,and/or energy associated with the antennas comprising cellular basestation, wireless handsets 114 and the like. As the wireless handset 114moves toward the outer range of the mobile carrier network 110, thestrength of the cellular signals degrade.

Similarly, an IP based data network 122 like the Internet 101 mayprovide wireless connectivity to wireless handsets 114 within range ofan IP access point 120. For instance, an IP access point 120 may providewireless connectivity using any of the 802.11 WiFi standards and/or anyother type of IP based connectivity standard. As will be appreciated bythose of skill in the art, a wireless handset 114 may experience astronger connection signal when located closer to an IP access point 120than when located further away from the IP access point 120. Thus, thestrength of the wireless data connection may fade as the wirelesshandset 114 moves away from an IP access point 120.

There may also be one or more alternative networks 115 that may provideaccess to the Internet 101 for a hybrid mobile device 124 or otherwireless handset devices 114. One such alternative network 115 may becharacterized as a WiMax network operable over the 802.16 wirelessprotocol standard. Another such alternative network 115 may becharacterized as a whitespace network. A whitespace network may utilizeRF spectrum that is shared with television broadcasters. The televisionbroadcasters do not necessarily need to utilize all the spectrumallocated to them to broadcast their video signals. The unused spectrummay be tapped into to provide an alternative RF access point to analternative network 115 that can interface with the Internet 101.

The collection of IP based data networks illustrated in FIG. 1 such asLAN/WANs 122, and the Internet 101 all run on a packet based datatransfer protocol characterized as packet switching. Packet switchingessentially chops up a data stream (e.g., text, voice, data) intosegments and transfers them across an IP network to a destination wherethe packets are re-assembled into the original data stream for output.Voice over IP (VoIP) is a specialized subset of IP packet basedcommunication directed to IP telephony. End user devices 118 utilize anIP access point 120 to access the larger IP network. The IP access point120 may be wired, wireless (e.g., WiFi), or a combination wired/wirelessaccess point such as those illustrated in FIG. 1. A VoIP communicationdevice 118 may communicate with an IP access point 120 to gain access tothe larger IP network 101 and other communication devices. The VoIPcommunication device 118 has been illustrated as a wireline type devicebut may just as easily be a wireless device communicable with the IPaccess point 120 over, for instance, one or more of the 802.11protocols.

In certain embodiments, mobile carrier network(s) 110 include cellularnetworks or portions of cellular networks based on GSM, LTE, CDMA,and/or any other cellular network standards. IP based data networks 122,101 include, for example, the Internet, one or more intranets, wide areanetworks (WANs), local area networks (LANs), and the like, portions orall of which may be wireless and/or wired. For instance, an IP baseddata network 122, 101 may be a wireless network or a portion of awireless network implemented using an IEEE 802.11 standard, WiMAX,and/or any other wireless data communication standard. As is known inthe art, the resources the various networks 108 (PSTN), 110 (MobileCarrier), 122, 101 (IP Based) may interface with the call server 102through gateway devices, routers and/or other appropriate devices (notshown). Similarly, the wireless handsets 114 may interface with thevarious networks 108 (PSTN), 110 (Mobile Carrier), 122, 101 (IP based)and alternative networks 115 through appropriate access points 111, 120(some not shown).

As one may surmise, it is far less complicated when both communicationdevices in a communication system utilize the exact same network. Forinstance, POTS phone to POTS phone would communicate over the PSTN onlywhile a GSM wireless handset to another GSM wireless handset of the samemobile service provider may be handled within the mobile carriernetwork. Lastly, a VoIP phone calling another VoIP phone would stayexclusively on a packet based series of networks like LAN/WANs, 122and/or the Internet 101.

Things get more complicated when the communication devices areassociated with different networks. For instance, a POTS phone placing acall to a wireless handset or a VoIP phone calling a POTS phone. Inthese scenarios, and others, there is an interface between the networksthat serves to resolve any differences so that a communication sessionmay be connected and maintained. As described above there may be anintervening network between two endpoint networks. For instance, eachmobile carrier network 110 includes an interface to the PSTN 108 suchthat calls crossing that interface can be handled by the receivingnetwork whether it is a mobile carrier network 110 or the PSTN 108.Similarly, each VoIP service provider on an IP packet based network 122,101 includes an interface to the PSTN 108 such that calls crossing thatinterface can be handled by the receiving network whether it is an IPpacket based network 122, 101 or the PSTN 108. Thus, the PSTN 108 servesas a common routing network for endpoint communication devices that areassociated with other networks. It is possible to create a VoIPinterface such that IP packet based networks 122, 101 can interfacedirectly with mobile carrier networks 110.

There is one aspect that each network (e.g, PSTN 108, VoIP 101, 122 andmobile carrier 110) has in common that facilitates communicationsessions among communication devices native to the various networks. Thecommonality is that each communication device has a unique telephonenumber (TN) as an identifier. The format of the telephone number isidentical regardless of the network in use. In North America, forinstance, the TN is a ten-digit number. Each communication device inNorth America is associated with a 10-digit telephone number thatsubscribers ‘dial’ to reach other subscribers no matter the network theother subscriber uses. Thus, users of communication devices need notworry about how to reach another user because all communication deviceskey off an associated telephone number. From the user's perspective, itis up to the networks to resolve any connection issues and allow callsto be connected so that a communication session may occur. For the mostpart, these network differences have been resolved on an industry widescale and it is relatively routine to place and connect calls betweenendpoints regardless of their native networks.

Each network service provider may provide equipment (communicationdevices) and service plans to its subscribers. These service plans canvary greatly in cost depending on the expected use of network resources.In addition, some service plans may bundle data and voice services inthe cost of the service plan. This is often the case for mobile carriernetwork 110 subscribers since the ability to access data networks suchas the Internet on a mobile device is a desired service. This isespecially the case when a WiFi data connection is out of range. As aresult, bundled voice and data services can place a significant burdenon the mobile carrier network resources that can lead to userestrictions for bundled voice/data plans.

One approach that addresses the mobile network congestion problem is acommunication device that may be characterized as a hybrid mobile device124. The hybrid mobile device 124 may be associated with networkinfrastructure that defaults telephony services to a WiFi connection 123using, for instance, VoIP over an 802.11 protocol via an IP access point120. The hybrid mobile device 124 may default to WiFi mode whenavailable and may only switch to a mobile carrier network 110 connectionvia a radio transmission scheme 125 to a basestation 112 (cellular mode)when the WiFi connection 123 is lost, is unavailable or degrades inquality to the point that the connection can no longer support telephonyservices. As it pertains to data, this heterogeneous network switchingmay be referred to as WiFi offloading. For telephony services, however,such a soft handover between heterogeneous networks is a more dauntingand complex process.

One implementation of a soft handover of a voice call betweenheterogeneous networks involves associating two telephone numbers to ahybrid mobile device 124. A first telephone number may be characterizedas a ‘data’ telephone number that is based on a VoIP telephony scheme.The second number may be characterized as a ‘mobile’ telephone numberthat is used in conjunction with a radio transmission scheme 125associated with a mobile carrier network 110. The subscriber may only beaware of the data number and not have actual knowledge of the mobilenumber. For all intents and purposes, the subscriber places and receivescalls using the data telephone number. To reach the subscriber, a secondcommunication device would dial the subscriber's data telephone number.

When the hybrid mobile device 124 is connected with an IP access point120, telephony services and functions are handled using VoIP. To dialout, the subscriber dials the telephone number of the intendedrecipient's communication device. The intelligence within the hybridmobile device 124 recognizes that the subscriber is attempting to placea call and notes the telephone number entered. The call from the hybridmobile device 124 is routed to a call server 102 hosted in an IP basednetwork 101 such as the Internet and establishes a first communicationlink. The call server 102 then determines the intended telephone numberthat was dialed by the subscriber and places a call to the communicationdevice associated with that telephone number (called communicationdevice). Upon connecting the second communication link between the callserver and the called communication device, the call server 102 joinsthe first communication link with the second communication link tocreate a full-duplex communication session between the hybrid mobiledevice 124 and the called communication device.

The communication session will generally stay active until one of therespective communication devices terminates the call. Sometimes,however, the hybrid mobile device 124 may experience a loss of servicewith or degradation to the WiFi connection. This commonly occurs if thehybrid mobile device 124 moves out of range of the IP access point 120or the quality of the connection with the IP access point 120 otherwisedegrades. In such a scenario, it is necessary to handoff or hand overthe call over to the mobile carrier network 110 to avoid terminating thecommunication session. This may be accomplished by creating a thirdcommunication link between the call server 102 and the hybrid mobiledevice 124. The third communication link, however, may be routed throughthe mobile carrier network 110 to the hybrid mobile device 124. When thefirst communication link is lost or is significantly degraded, it may beseamlessly replaced by the third communication link such that the callserver 102 bridges or connects the third communication link with thesecond communication link to maintain the communication session.

Determining when to handoff the call to the mobile carrier network 110may be based on any number of suitable factors. In a typicalimplementation, a manufacturer, carrier or network provider maydetermine a default set of connection characteristics below which aconnection is handed off from the IP network 101 to the mobile carriernetwork 110. This default approach, however, may not take into accountthe differences between user expectations regarding connection quality,differences in networks configurations and performance capabilities, anddifferences between devices used to establish the connection on behalfof a user (e.g. different mobile devices). Based on these and otherfactors, as described in more detail below, it may be advantageous toincorporate user feedback into the algorithm used to determine when thehandoff from the IP network 101 to the mobile carrier network 110 (or analternative network 115 via an alternative network access point 111 or adifferent WiFi IP access point 120 for which network conditions may bemore favorable) is required.

On inbound calls to the hybrid mobile device 124, a callingcommunication device dials the data number of the hybrid mobile device124. This initiates a connection to the call server 102 as the datanumber is automatically routed to the call server 102. The call serverthen establishes a first communication link with the callingcommunication device. The call server 102 then establishes a secondcommunication link with the hybrid mobile device 124. The call serverdefaults to WiFi mode in attempting to establish the communication linkwith the hybrid mobile device 124. If the hybrid mobile device 124 isnot currently connected to an IP access point 120 and is thereforeinaccessible via VoIP over WiFi, the call server will switch to cellularmode. In cellular mode, the call server will establish the secondcommunication link over the mobile carrier network 110. This cannot bedone, however, using the hybrid mobile device's 124 data number sincethat number is unknown to the mobile carrier network 110. To establishthe second communication link between the call server 102 and the hybridmobile device 124, the call server accesses a translation table within adatabase that includes data/mobile number pairs in which each pair maybe associated with a hybrid mobile device 124. In this case, the callserver will lookup the data number and have a mobile number returned.The call server 102 may then establish the second communication link bydialing the mobile number and establishing a connection to the hybridmobile device 124. The call server may then join the first and secondcommunication links to create the full-duplex communication sessionbetween the calling device and the hybrid mobile device 124.

The communication session will stay active until one of the respectivecommunication devices terminates the call. While the communicationsession is in progress, the hybrid mobile device 124 may re-establish aWiFi connection. In such a scenario, it may be desirable to hand thecall over to the VoIP network to reduce the burden on the mobile carriernetwork 110. This may be accomplished by creating a third communicationlink between the call server 102 and the hybrid mobile device 124. Thistime the third communication link may be routed over the VoIP network101, 122 via an IP access point 120 to the hybrid mobile device 124.When the third communication link is sufficiently established, it mayseamlessly replace the first communication link such that the callserver 102 bridges or connects the third communication link with thesecond communication link to maintain the communication session.

In another outbound calling scenario, the hybrid mobile device 124 maynot have an initial connection via WiFi to a packet based VoIP network122, 101 or the WiFi connection may not be sufficiently good. Anoutbound call to a destination telephone number is established over themobile carrier network 110 using the mobile number associated with thehybrid mobile device 124. For caller ID purposes, however, the callingnumber is the data number associated with the hybrid mobile device 124.The call is again routed to and through the call server 102. The firstcommunication link is between the hybrid mobile device 124 and the callserver. This is accomplished by having the hybrid mobile device 124automatically place a call to the call server 102 using one of the poolof telephone numbers associated with the call server. Just prior to thecall, the hybrid mobile device 124 may utilize the mobile carriernetwork's data services to send a message to the call server 102. Themessage to the call server 102 may contain the mobile and data numbersof the hybrid mobile device 124 and the destination telephone numbersuch that when the call server 102 receives the call from the hybridmobile device 124 using the mobile number, it can place a call to thedestination telephone number and substitute the data telephone number inthe caller ID field. Upon establishing the second communication link,the call server 102 may then join the first and second communicationlinks to create the full-duplex communication session between the hybridmobile device 124 and the destination device.

FIG. 2 is a block diagram illustrating some of the functions of the callserver according to one or more embodiments described herein. The callserver 102 may comprise, for example, a server computer or any othersystem having computing capability. The schematic block diagram showsthat the call server 102 may include at least one processor component103 (“processor 103” hereinafter), at least one communication interface109 (e.g., a network interface card or the like), and a data storagecomponent 105, each of which is coupled to a local interface 113. Thelocal interface 113 may comprise, for example, a data bus with anaccompanying address/control bus or other bus structure as can beappreciated. Stored in the data storage component 105 are a memory 107and multiple components 102 a-102 c (e.g., software applications) thatare executable by the processor 103 and that provide at least some ofthe functionality of the call server 102.

Alternatively, a plurality of call servers 102 may be employed and maybe arranged, for example, in one or more server banks or computer banksor other arrangements. For example, a plurality of call servers 102together may comprise a cloud computing resource, a grid computingresource, and/or any other aggregated or distributed computingarrangement. Such call servers 102 may be located in a singleinstallation or may be distributed among different geographicallocations. For purposes of convenience, the call server 102 isillustrated in FIGS. 1 and 2 and referred to herein in the singular.Even though the call server 102 is referred to in the singular, it isunderstood that a plurality of call servers 102 may be employed invarious arrangements as described above.

The communication interface(s) 109 may include a voice-over-IP (VoIP)interface 106 adapted to exchange IP based telephony signaling (e.g.,SIP) and/or media data with other IP network devices using a VoIPprotocol. Another communication interface 109 may be a PSTN interface104 adapted to convert incoming PSTN audio data to VoIP audio data andconvert outgoing VoIP audio data to PSTN audio data. Still anothercommunication interface 109 may be an IP data interface 117 adapted toexchange IP data with other IP network devices. This may include IP dataexchanged with a mobile wireless handset 114, 124 over an intermediatemobile carrier network 110. Yet another communication network interface109 may be directed toward an alternative network 115 adapted toexchange data with a wireless handset 114 or a hybrid mobile device 124.Examples of alternative network(s) 115 may include, but are not limitedto, WiMax and whitespace. A whitespace network may be characterized asone that utilizes frequency spectrum that is overlapping with that ofbroadcast television frequency spectrum.

The call server 102 may further include several inter-operable softwaremodules operable with application programming interfaces (APIs) 121 andcommunication interfaces 109 and configured to intelligently manage thecommunication session. These software modules may include abridge/routing module 102 a, an intelligence module 102 b, and a handoffmodule 102 c. The aforementioned software modules have functional namesfor convenience and ease of reference. These functional names should notbe construed as limiting to the various software modules individually orthe call server 102 as a whole. There may be functions performed by oneor more of the software modules in conjunction with the APIs 121 andnetwork communication interfaces 109 that achieve a stated purpose orgoal.

The bridge/routing module 102 a may be configured to physically orlogically connect communication links. The intelligence module 102 b maybe configured to monitor network conditions and receive communicationsession data from the hybrid mobile device 124 regarding its connectionwith the IP access point 120 so as to intelligently determine the needfor a soft handoff to the mobile carrier network 110. Communicationsession data may refer to any data relating to a communication sessionor its constituent communication link(s), such as, but not limited to,detected signal strengths, available networks, protocol and bufferstatistics and analysis, environmental and/or geographical factors, theperformance of access points and other network components, pastinteractions between or among communication devices, access points andother network components, context of conversations during voice calls,and other data points described herein. The call handoff module 102 cmay be configured to initiate a handoff from one communication link toanother communication link with the assistance of the bridge/routingmodule 102 a and the intelligence module 102 b. The details of the callhandoff procedure supported by the call handoff module 102 c, includingthe incorporation of user feedback, is described in more detail below.

More specifically, the bridge/routing module 102 a may cooperate withthe APIs and network interfaces to physically or logically connectcommunication links to initially establish a communication sessionbetween communication devices and/or to perform a handoff of at leastone communication link of a communication session from one network toanother network. A communication session may be, for instance, between ahybrid mobile device 124 and a second telephony endpoint (e.g., 114,116, 118). The handoff may be caused by an instruction or commandreceived from the call handoff module 102 c. The bridge/routing module102 a may be configured to physically or logically establishcommunication links, join communication links, and sever communicationlinks to a common or shared communication session based on commands orinstructions received from the call server 102.

The intelligence module 102 b may cooperate with the APIs and networkinterfaces to monitor and gather (receive) data pertaining to networkconditions and communication device connections with various networks.The data may then be intelligently processed to predict or determine theneed for a handoff of at least one communication link of a communicationsession. The data received by the intelligence module 102 b may includeout of band and/or out of network signaling from a communication deviceto indicate that a handoff is needed. In such a case, the intelligencemodule 102 b may instruct the call server 102 to establish a newcommunication link via the bridge/routing module 102 a and then instructthe call handoff module 102 c to initiate a handoff process once the newcommunication link has been established.

The call handoff module 102 c may cooperate with the APIs and networkinterfaces to effect a handoff of a first communication link between thecall server 102 and the hybrid mobile device 124 to a secondcommunication link between the call server 102 and the hybrid mobiledevice 124. The call handoff module 102 c may receive data andinstructions from the intelligence module 102 b that indicates a handoffmay be needed imminently based on the degrading network conditionsassociated with the first communication link. The need may be determinedbased on a handoff profile established based on a pre-defined defaulthandoff profile or user feedback regarding the quality of thecommunication link. The call handoff module 102 c may then executecertain instructions to establish a second communication link betweenthe call server 102 and the hybrid mobile device 124. Once the secondcommunication link has been established, the call handoff module 102 cmay instruct the bridge/routing module 102 a to join the secondcommunication link to the communication session with the other telephonydevice (114, 116, 118) prior to severing the first communication linkbetween the call server 102 and the hybrid mobile device 124.

The call handoff module 102 c may also include communication linkhandoff logic (CLH) designed to receive and process user feedbackpertaining to call quality parameters of a media stream between acommunication device and the call server 102. The call server 102 CLHlogic may include, for example, logic to establish a handoff profilebased at least in part on user feedback regarding communication linkquality.

The call server 102 may execute various applications and/or otherfunctionality for, among other things, setting-up, managing andtearing-down communication sessions between communication devices 124and 114, 116, 118. Also, various data may be stored in a data storage105 via memory 107 of the call server 102. Data storage 105 illustratedin FIG. 2 may be representative of a plurality of data stores, as can beappreciated. The data stored in the data storage 105, for example, maybe associated with the operation of the various applications and/orfunctional entities of the call server 102.

FIG. 3 is a block diagram illustrating a hybrid mobile device 124according to one or more embodiments described herein. The hybrid mobiledevice 124 may include a processor component or processor(s) 305 forcontrolling the various components and functions of the hybrid mobiledevice 124. The hybrid mobile device 124 may also include multiple RFtransceivers such as, for instance, a WiFi transceiver 310, a cellulartransceiver 315, and an alternate transceiver 320.

The WiFi transceiver 310 may be operable to communicate with an IPnetwork access point 120 using one or more of the 802.11 wirelesstransmission protocols. Upon connection with an IP network access point120, the hybrid mobile device 124 may exchange IP data with servers orother computers that are connected with or communicable with theInternet 101 via LAN/WAN 122. This may include the call server 102 shownin FIG. 1.

The cellular transceiver 315 may be operable to communicate with amobile carrier network 110 for both voice and IP data communication. Onthe voice side, the mobile carrier network 110 may be based on GSM,CDMA, or other communication protocols while on the IP data side, themobile carrier network 110 may be based on, for example, GPRS, EDGE,EV-DO, HSPA-D, HSPA-U, LTE, UMTS-WCDMA, UMTS-TDD, eHRPD etc.

In one embodiment, the alternate transceiver 320 may be a WiMaxtransceiver that is operable to communicate with an IP network accesspoint using one or more of the 802.16 wireless transmission protocols.Upon connection with a WiMax network access point, the hybrid mobiledevice 124 may exchange IP data with servers or other computers that areconnected with or communicable with the Internet 101 via WiMax network115. This may include call server 102 shown in FIG. 1. In anotherembodiment, the alternate transceiver 320 may be a whitespacetransceiver that is operable to communicate with a whitespace networkaccess point. The whitespace network, in turn, may be communicable withthe Internet 101 to allow IP data communication between the hybridmobile device 124 and servers or other computers that are connected withor communicable with the Internet 115. This may include call server 102shown in FIG. 1.

The hybrid mobile device 124 may further include data storage 325,software applications 330, various user interface(s) 335 andcommunication link handoff (CLH) logic 340. The data storage 325 mayinclude, for example, one or more types of memory devices including, butnot limited to, flash memory usable for ROM, RAM, PROM, EEPROM, andcache. The software applications 330 may include, for example, one ormore software applications executable on or by the processor(s) 305including, but not limited to, web browsers, email applications,application specific data and/or audio/video applications, call handoffapplications, etc. The user interface(s) 335 may include, for example, adisplay, a touchscreen for soft-key input, speaker(s), microphone(s), akeyboard for hard-key input, and one or more buttons. The CLH logic 340may include, for example, logic to establish a handoff profile based atleast in part on user feedback regarding communication link quality.

FIG. 4 is a block diagram illustrating a communication session handoffbetween a hybrid mobile device 124 and a call server 102 utilizingdifferent networks 510, 520 according to one or more embodimentsdescribed herein. Once a call has been established between a hybridmobile device 124 and another communication device 410 with the callserver 102 acting as a bridge connecting the two communication devices,the communication session will stay active until one of the respectivecommunication devices terminates the call.

Sometimes, however, the hybrid mobile device 124 may experience a lossof service with or degradation to the original network 510 connectionused to establish the call. The original network 510 may be a mobilecarrier network 110 or an IP network 122/101. In such a scenario, it isnecessary to hand the call over (e.g., handoff) to an alternate network520 to avoid terminating the communication session. The alternatenetwork 520 may be the opposite of the original network 510. Forexample, if the original network 510 was an IP network 122/101, thealternate network 520 maybe a mobile carrier network 110 and vice versa.The embodiments are not limited to these examples. There may be otheralternate network(s) 520 that are neither mobile carrier network(s) 110or IP network(s) 122/101.

The handoff may be accomplished by creating an alternate communicationlink between the call server 102 and the hybrid mobile device 124. Thealternate communication link, however, will be routed through thealternate network 520 to the hybrid mobile device 124. When the originalcommunication link is lost or is significantly degraded, it may beseamlessly replaced by the alternate communication link such that thecall server 102 bridges or connects the alternate communication linkwith the communication link to the other communication device 410 tomaintain the communication session.

To establish the alternate communication link, the hybrid mobile device124 may initially send an out of band or even an out of network signalto the call server 102. A call between the hybrid mobile device 124 anda called communication device 410 by way of call server 102 may beinitially setup using the Session Initiation Protocol (SIP). IPaddresses and ports are exchanged and an audio (and/or video) codec isnegotiated for the exchange of media. Audio (and/or video) from bothends flows using the Real-time Transport Protocol (RTP) and the selectedcodec(s). Any further change in the call is accomplished using SIP(e.g., one party hangs up). The hybrid mobile device 124 may alsomaintain an open data channel with the call server 102 using, forexample, a protocol called Message Queue Telemetry Transport (MQTT).MQTT is an open message protocol for machine-to-machine communicationthat enables the transfer of telemetry-style data in the form ofmessages from pervasive devices, along high latency or constrainednetworks, to a server or small message broker. Pervasive devices mayrange from, for example, sensors and actuators, to mobile phones,embedded systems on vehicles, or laptops and full-scale computers.

The MQTT channel is not involved in the initial call setup. As long asthe communication device has some sort of network connection, the MQTTchannel is available. The impending handoff signal may be sent from thecommunication device to the server using this data channel. The MQTTchannel is out of band in the sense that it is not involved with theinitiation or destruction of a communication session (e.g., phone call).Nor is it in the path of the exchange of media between the hybrid mobiledevice 124 and the call server 102. Additionally or alternatively, theimpending handoff signal could be out of band in the sense that it usesan alternative such as, for example, a text message, white space, or LTEthat may be referred to herein as out of network signals.

The out of band or out of network signal may instruct the call server102 to initiate the process of establishing an alternate communicationlink between the hybrid mobile device 124 and the call server 102. Theout of band or out of network signal may be the result of the hybridmobile device 124 detecting poor or degrading original networkconnectivity or may be based on one or more other sensor inputsindicative of the impending need for a handoff. Once the out of band orout of network signal requesting establishment of an alternatecommunication link is received, the call server 102 may initiate thealternate communication link by first determining on what network theoriginal communication link is established. The call server 102 may thendial the hybrid mobile device 124 using the telephone number associatedwith the alternate network connection 520 to the hybrid mobile device124. The hybrid mobile device 124 may then automatically answer the callwithout user notification or intervention. The call server 102 may thenjoin the alternate communication link with communication link to theother communication device 410 to maintain the communication sessionbefore severing the original communication link between hybrid mobiledevice 124 and the call server 102. Alternatively, the hybrid mobiledevice 124 may sever the original communication link once the alternatecommunication link is established.

For example, if the original network connection 510 for the originalcommunication link is a VoIP based WiFi connection, the alternatecommunication link may be established over a mobile carrier network viaa cellular system. The hybrid mobile device 124 will have both a datatelephone number associated with, in this example, the original network510 and a mobile telephone number associated with the alternate network520. The alternate communication link may be routed over the alternatenetwork 520 by having the call server 102 send call establishmentsignaling to the hybrid mobile device 124. Since the hybrid mobiledevice 124 is currently connected to the call server on the originalcommunication link, the incoming new call signaling may be acted uponwithout notifying the user. For instance, the hybrid mobile device 124may not ring, vibrate, or display a call waiting message pertaining tothe incoming call from the call server 102. Rather, the hybrid mobiledevice 124 may automatically answer the new incoming call over thealternate network 520 based on a particular piece of information in thesignaling data that identifies the new call as being a handoff for thecurrent call. For example, the out of band or out of network signal sentby the hybrid mobile device 124 to the call server 102 may include aflag or data bits uniquely signifying a request to create an alternatecommunication link between the hybrid mobile device 124 and the callserver 102 and switch from the original communication link to thealternate communication link. In another embodiment, the call server mayuse a particular telephone number as the source number when signalingthe hybrid mobile device 124. The particular number may be dedicated tohandoff calls only.

The technique(s) described may work whether the original network 510 isan IP based VoIP network 122/101 and the alternate network 520 is acellular based mobile carrier network 110 or vice versa. In addition,there may be other types of non-cellular based network(s) that canfunction as the original network 510 or alternate network 520. Theembodiments are not limited to these examples.

The foregoing description relates generally to the process of handing acall off from an IP based VoIP network 101 to a cellular based carriernetwork 110 or an alternate network 520 (and vice versa). While thehandoff process itself is useful in improving the user experience anddecreasing network load by utilizing an IP based VoIP network 101 whenpossible, the determination regarding when to initiate the handoff andwhat parameters to analyze when determining that the handoff should beperformed is an area that can be improved. Currently, a devicemanufacturer, network carrier or other similar party in thecommunications chain assigns default handoff metrics. This process,however, does not account for personal user preferences, user tolerancefor communication link quality degradation, variations between differentnetworks and devices and the like. Therefore, in various embodiments itmay be advantageous to incorporate user feedback into the algorithm usedto determine when a handoff should occur for that user. In addition, alarger data set of user feedback may also be used to refine a default(or current) handoff profile. The embodiments are not limited in thisrespect.

In various embodiments, a communication link may be established betweena first communication device and a call server operable in an InternetProtocol (IP) based packet data network. In some embodiments, thiscommunication link may comprise an actual call. In other embodiments,this communication link may comprise a test call established for thepurpose of establishing user preferences regarding communication linkquality. In still other embodiments, the communication link may be asimulated test call performed over an Internet connection between aserver and a web browser or by a software application executing on auser's communication device.

During the course of the communication link (e.g. while thecommunication link is active), user feedback may be received indicatinga level of quality of the communication link. For example, as shown inFIG. 5A, the user feedback may comprise activation of one or moreinput/output (I/O) devices 502 of the first communication device (e.g.mobile device) 124. In the example 500 shown in FIG. 5A, a user 504 maypress and hold the down volume button 502 to indicate that the qualityof the connection link is not personally sufficient. In otherembodiments, as shown in FIG. 5B for example, the user feedback maycomprise interaction with a graphical user interface (GUI) element 556displayed on a touch sensitive display 554 of the first communicationdevice (e.g. mobile device) 124. For example, if the user is utilizingspeakerphone mode or a headset device (not shown), the user may haveaccess to the touch sensitive display 602 during the connection link. Inthese example, the user may be presented with a graphical user interfaceelement 556 that when pressed may indicate a personal evaluation ofinsufficient connection link quality as judged by the user. In stillother embodiments, while not shown, the user feedback may compriseactivation of one or more sensors of the first communication device(e.g. mobile device 124). For example, a user may be instructed to shakeor rotate the first communication device to indicate insufficientcommunication link quality as judged by the user, and one or moresensors of the first communication device, such as one or moreaccelerometers, may detect this movement. The embodiments are notlimited in this context.

In the case of an actual call (e.g. a connection between two users), theuser feedback may be provided in response to a loss of call/connectionquality to the point that the connection is no longer sufficient tosatisfy the user's call quality expectations. For example, a loss of afew packets may not bother some users while other users may find thisquality loss to be unacceptable. In the case of a test call or testcommunication link or a simulated communication link, one or morecommunication link parameters may be varied, regardless of the actualquality of the communication link, that affect the quality of thecommunication link to present varying communication link quality levels.Regardless of the type of connection, user feedback with respect tocommunication link parameters may be received in response to the changesin the quality of the communication link.

When user feedback is received, one or more communication linkparameters may be determined and recorded. For example, thecommunication link parameters may comprise one or more of receivedsignal strength (e.g. via a RSSI), jitter, latency, packet loss, linkspeed, link throughput or distance between the first communicationdevice and an IP access point. While a limited number and type ofcommunication link parameters are described for purposes ofillustration, it should be understood that the embodiments are notlimited in this respect.

In various embodiments, latency (e.g., delay) may comprise a one-waydelay between a source and destination. VoIP is a real-time applicationthat cannot tolerate long delays as the users will lose interactivity.According to the International Telecommunication Union-TelecommunicationStandardization Sector (ITU-T) recommendations, one-way delay followsthe following constraints: under 150 ms is acceptable; 150 to 400 ms isacceptable with limitations; and over 400 ms is unacceptable. In a VoIPtelephony system, voice packets are transmitted by RTP. RTP identifies avoice stream by its unique Synchronization Source Identifier (SSRC).Additionally, individual packets can be identified by the port numbers,sequence numbers and timestamps. The time difference of the same packetat source and destination results in its one-way delay.

Jitter comprises the variation in delay of successive voice packets.Jitter occurs because different packets suffer different delays in thenetwork. Jitter contributes in the overall delay of the voice packets.It is an estimate of the inter-arrival time of RTP packets and may bereferred to as the inter-arrival jitter. If R represents the arrivaltime of a packet and S represents the RTP timestamp, then theinter-arrival difference D(i,j) between two packets i and j can becalculated as follows:D(i,j)=(R _(j) −R _(i))−(S _(j) −S _(i))=(R _(j) −S _(j))−(R _(i) −S_(i))

Packet loss may also be a dominant factor in the loss of quality in aVoIP communication link. Packet loss is generally intolerable in timeconstrained applications like VoIP. Packet loss can be annoying becausevoice packets are carried by User Datagram Protocol (UDP) that does notretransmit lost packets. Packet loss may be due to congestion,interference, noise and buffer overflow at the receiver. A packetarriving after a certain scheduled play out time is also discarded.Packet loss can be mitigated using forward error correction (FEC) bytransmitting redundant information and interleaving the packets.Typically, packet loss up to 10% may be acceptable in VoIPcommunications.

In various embodiments, an increased distance between a hybrid mobiledevice 124 and an IP access point 120 may result in decreasedcommunication link quality. For example, the further a hybrid mobiledevice 124 is moved away from an IP access point 120, the lower thequality of the communication link. This decrease in quality can bemeasured, at least in part, based on signal strength via, for example,RSSI. Other embodiments are described and claimed. These and othercommunication link parameters may be measured and recorded at the time(or shortly thereafter) user feedback is received.

The one or more communication link parameters may be correlated to aloss of quality of the communication link in some embodiments. Forexample, when a user indicates that the quality of a communication linkhas degraded, the one or more communication link parameters may berecorded and associated with a loss of quality of a communication link.A handoff profile may be established based on the user tolerance levelsfor various communication link parameters.

In various embodiments, a personalized handoff profile may comprise aminimum desired quality of the communication link for a voice call. Thecommunication link may be handed off to an alternate communication linkusing an alternate network while maintaining a connection between thehybrid mobile device 124 and the call server 102 when the quality of theoriginal communication link dips below the handoff profile. For example,based on the user feedback described above, a handoff profile containingthreshold levels associated with individual communication linkparameters may be assigned to the hybrid mobile device 124 at which theuser provides the feedback. In this example, the handoff profile may becustomized for a particular user or on a per user basis. In otherembodiments, the handoff profile data may be sent to one or more callservers 102 along with the handoff profile data of other users toaverage the handoff profile data. The collective user data may establisha community handoff profile that may be used as an initial defaulthandoff profile for all subsequent users. In this example, the handoffprofile data may be crowd sourced such that the data comprises anaverage of different preferences, experiences and quality considerationsacross any number of users. The embodiments are not limited in thisrespect.

The handoff profile comprises threshold levels for various communicationlink parameters such that when one of the communication link parametersdips below its threshold level, initiation of a handoff of thecommunication link from the current network to an alternate network maybe commenced. It may not be necessary to wait until a single parametercrosses its particular threshold to initiate a handoff, however. If morethan one communication link parameter is within a pre-defined tolerancerange of its threshold level, a handoff may be initiated. For example iftwo parameters are approaching their respective threshold levels, itcould be indicative that the communication link is breaking down on morethan one front. Rather than wait until one of them actually reaches itsthreshold, a handoff may be initiated if both exhibit a level that iswithin a pre-defined range of the threshold level. The pre-defined rangemay be adjusted based on the type and number of communication linkparameters that are approaching the threshold level.

In another embodiment, the handoff profile may be a normalized scorebetween 1-100 for example in which each communication link parametercontributes to the normalized score. For example, jitter may comprise30% of the normalized score while packet loss comprises 40%, and latency30%. A handoff may occur when the normalized score falls below athreshold. The threshold may be determined based on user feedback to theindividual communication link parameters. In this example, user feedbackmay have indicated that the user reacts negatively when jitter is 20%below optimum, latency is 15% below optimum, and packet loss is 25%below optimum levels. A pre-defined tolerance range (e.g., a 10%variance from the individual threshold) may be built into thecombination of communication link parameters to account for thecombination effect since crossing any individual communication linkparameter threshold would also trigger a handoff. This may translate toa normalized combinational threshold of:Jitter=30*0.80=24+10%=26.4Latency=30*0.85=25.5+10%=27.05Packet Loss=40*0.75=30+10%=33Combinational Threshold=26.4+27.05+33=86.45Anytime during subsequent calls in which the hybrid mobile device 124has a VoIP communication link with the call server 102, a handoff may beinitiated when the detected normalized score for the currentcommunication link parameters falls below 86.45 as per the user feedbackdefined combinational threshold.

The example above is purely exemplary. Other combinations, percentages,and rankings of the communication link parameters with respect to anormalized score and threshold may be implemented.

A hybrid mobile device 124 as described herein may include a mechanismto force a manual handoff from an IP network 122 to a mobile carriernetwork 110 (e.g., cellular network) in some embodiments. In theseembodiments, in response to receiving a request to handoff thecommunication link to an alternate communication link using an alternatenetwork such as a mobile carrier network 110, one or more communicationlink parameters may be determined and the handoff profile may beestablished based on the request. For example, rather than requestingspecific feedback from a user during a call, the system may use therequest for a manual handoff as the feedback to capture the informationneeded to establish and/or update the handoff profile. In thisembodiment, the values of the communication link parameters may berecorded at the time of manual handoff request and treated as userfeedback for creating a handoff profile. Subsequent calls exhibitingcommunication link parameters like those at the time of the manualhandoff request may initiate an automatic handoff.

In other embodiments the call server may include logic operable tosimulate a test call with a user via a web browser. For example, priorto purchasing a hybrid mobile device 124, a user may have the option ofestablishing a test call via a tablet computing device, laptop or othersimilar computing device to determine or estimate the call quality thatwould be expected should the user decide to purchase a hybrid device. Inthese examples, a user may have the opportunity to place a test callover a home network and over a work network to ensure that the mostcommonly used IP networks provide sufficient call quality for VoIP callsprior to incurring the expense of purchasing a hybrid mobile device 124.

In another embodiment, the call server 102 may simulate the effects ofthe various communication link parameters and solicit user feedback. Forexample, the call server may establish a communication link with thehybrid mobile device 124 by creating an actual phone call with theuser's hybrid mobile device 124. The phone call may be established bythe user by calling a pre-determined telephone number associated withthe call server 102 and reserved for call quality evaluation purposes.In another embodiment, the user may select an option from a hybridmobile device 124 based software application that is directed toevaluating call quality. In selecting the option via a graphical userinterface (GUI), a phone call is made to the pre-determined telephonenumber or an instruction is sent to the call server 102 to call theuser's hybrid mobile device 124. Once the call is established, the callserver 102 may create an audio media stream and intentionally introducediminishing quality for parameters like packet loss, jitter, latency,etc. The call server 102 may request that the user indicate when aparticular communication link parameter has degraded to the point that ahandoff is desired. This may be achieved through a graphical userinterface (GUI) interaction of some sort. The call server 102 and/or thehybrid mobile device 124 may then create a default handoff profile forthe user based on the feedback. The handoff algorithm may then beadjusted for that user and implemented for the hybrid mobile device 124.This procedure may be repeated by the user as often as desired.

In another embodiment, a software application executing on the hybriddevice 124 may simulate the same communication link parameters andacquire feedback. This may be achieved through a graphical userinterface (GUI) interaction of some sort. An actual telephone call isnot required in this embodiment. The acquired feedback may be used bythe hybrid mobile device 124 to amend the user's handoff profile. Inaddition to or in lieu of, the acquired feedback may be sent to a callserver 102 that maintains user handoff profiles. The user may log in toan account associated with the service such that acquired feedback maybe linked to the proper user. Other embodiments are described andclaimed.

In various embodiments, the foregoing functionality may be enabled bycommunication link handoff (CLH) logic present on either or both of thecall server 102 and hybrid mobile device 124. For example, at least onemachine-readable medium may comprise a set of instructions that inresponse to being executed on a computing device cause the computingdevice to perform any of the functionality, methods and/or processesdescribed herein. In some embodiments, an apparatus may comprise aprocessor component, at least two radio frequency (RF) transceivers eachcapable of communicating with a call server over a separate network, andcommunication link handoff (CLH) logic to be executed by the processorcomponent to perform any of the functionality, methods and/or processesdescribed herein. In other embodiments, a system may comprise aprocessor component, memory coupled to the processor component at leasttwo radio frequency (RF) transceivers each capable of communicating witha call server over a separate network, one or more antennas coupled tothe at least two RF transceivers, and communication link handoff (CLH)logic to be executed by the processor component to perform any of thefunctionality, methods and/or processes described herein. Theembodiments are not limited in this respect.

Included herein is a set of flow charts and message diagramsrepresentative of exemplary methodologies for performing novel aspectsof the disclosed architecture. While, for purposes of simplicity ofexplanation, the one or more methodologies shown herein, for example, inthe form of a flow chart or flow diagram, are shown and described as aseries of acts, it is to be understood and appreciated that themethodologies are not limited by the order of acts, as some acts may, inaccordance therewith, occur in a different order and/or concurrentlywith other acts from that shown and described herein. For example, thoseskilled in the art will understand and appreciate that a methodologycould alternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, not all acts illustratedin a methodology may be required for a novel implementation.

FIG. 6A illustrates an example of a first logic flow. As shown in FIG.6A, the first logic flow includes a logic flow 600. Logic flow 600 maybe representative of some or all of the operations executed by one ormore logic, features, or devices described herein, such as any devices,systems, methods and/or techniques described above with references toFIGS. 1-5B for example. More particularly, logic flow 600 may beimplemented by CLH logic 340 of a hybrid mobile device 124 or callserver 102 in some embodiments. In various embodiments, the logic flow600 may be representative of some or all of the operations associatedwith obtaining and utilizing user feedback to establish or update ahandoff profile based on a live call between two end users. Otherembodiments are described and claimed.

In the illustrated example shown in FIG. 6A, the logic flow may includea call server 102 mediating a voice media channel connection between ahybrid mobile device and a second device at 602. For example, the voicemedia channel connection may comprise a communication link between ahybrid mobile device 124 and a call server 102 operable in an InternetProtocol (IP) based packet data network 101 and between the call server102 and a second communication device 114, 116, 118. For example, acommunication link may be established between hybrid mobile device 124,call server 102, and a second communication device 114, 116, 118 in someembodiments.

At 604, the logic flow may include a call server 102 receiving userfeedback pertaining to voice quality over the media channel during thecall. For example, the user feedback received during the communicationlink may indicate a lack of quality of the communication link. If, insome embodiments, a user determines that the quality of the VoIPcommunication link less than desired for a VoIP call, the user may,among other things, hold down the down volume button for a designatedperiod of time to provide feedback. The feedback itself may be sent overa parallel data channel between the hybrid mobile device 124 and thecall server 102. Such a parallel data channel may include an MQTTchannel, and/or a cellular data channel. Another mechanism for conveyingthe in-call user feedback to the call server 102 may be automaticallyconstruct and send an SMS message to the call server 102 using either atelephone number or SMS short code associated with the call server 102as the destination. Other feedback mechanisms on the hybrid mobiledevice 124 may be implemented including manipulating other buttons onthe housing of the first communication device and/or interaction with atouch screen display. The embodiments are not limited in this respect.

The logic flow may include the call server 102 and/or firstcommunication device determining a user quality tolerance threshold forcommunication link parameters based on the user feedback at 606. In someembodiments, this may include determining one or more communication linkparameters in response to the user feedback wherein the CLH logic on thehybrid mobile device 124 or the call server 102 may be operative tomonitor, measure and/or record the one or more communication linkparameters such as jitter, latency, RSSI or the like in response toand/or at the time of receiving the user feedback indicating adegradation of VoIP call quality.

At 608, the logic flow may include the call server 102 and/or hybridmobile device 124 updating a handoff profile for the hybrid mobiledevice 124 based on the user quality tolerance thresholds ofcommunication link parameters. In various embodiments, the CLH logic maybe operative to correlate the one or more communication link parametersto the lack of quality of the communication link. For example, the userfeedback may trigger the CLH logic to record the one or morecommunication link parameters in response to the user feedback,associate these parameters with less than desired quality of thecommunication link and update the handoff profile of the hybrid mobiledevice 124 based on the communication link parameters accordingly.

At 610 the logic flow may include the call server 102 forwarding a newhandoff profile to the hybrid mobile device 124 or the hybrid mobiledevice 124 updating its own handoff profile. For example, a new handoffprofile may be established based on the correlating and this new handoffprofile may be forwarded to the hybrid mobile device 124 from which theuser feedback originated. The logic flow at 612 may include updating thehybrid mobile device 124 with the new handoff profile. For example, oncereceived, the hybrid mobile device 124 may utilize the new handoffprofile to make handoff decisions moving forward. In embodiments wherethe hybrid mobile device 124 calculated its own new handoff profileusing CLH logic based on the user feedback, the hybrid mobile device 124may update the handoff profile itself. The process may be repeated asoften as desired. Other embodiments are described and claimed.

FIG. 6B illustrates an example of a second logic flow. As shown in FIG.6B, the second logic flow includes a logic flow 620. Logic flow 620 maybe representative of some or all of the operations executed by one ormore logic, features, or devices described herein, such as any devices,systems, methods and/or techniques described above with references toFIGS. 1-5B for example. More particularly, logic flow 620 may beimplemented by CLH logic 340 of a mobile device 124 and/or call server102 in some embodiments. In various embodiments, the logic flow 620 maybe representative of some or all of the operations associated withcreating a specific call (e.g. a test call) between a hybrid mobiledevice 124 and a call server 102 wherein the call server simulatescommunication link parameters and/or changes in communication linkparameters and solicits feedback to establish or update a handoffprofile. Other embodiments are described and claimed.

At 622 the logic flow may include the call server 102 and hybrid mobiledevice 124 establishing a voice media channel connection specifically togauge a user's tolerance to communication link parameters. For example,rather than establishing a link between the hybrid device 124 and thecall server 102 for the purpose of connecting the hybrid device 124 to asecond communication device to enable users of the devices tocommunicate, the communication link may instead be established forpurposes of a test call. More particularly, the logic flow at 624 mayinclude the call server 102 varying multiple communication linkparameters (e.g. packet loss, jitter, latency, etc.). For example, aspart of the test call, the call server 102 may vary and/or simulatevariance of one or more communication link parameters to enable a userof the hybrid mobile device 124 to experience the differences inconnection quality associated with the changes. The embodiments are notlimited in this respect.

The logic flow at 626 may include the call server 102 requesting userfeedback for each communication link parameter. In some embodiments, thecall server 102 may individual adjust each communication link parameterand request user feedback for each adjustment. For example, jitter maybe gradually increased until user feedback is received, then latency maybe gradually increased until user feedback is received and so on. Inother embodiments, different combinations of changes among the differentcommunication link parameters may be combined and the differentcombinations may each be adjusted until user feedback is received.

The call server 102 and/or hybrid mobile device 124 may determine a userquality tolerance threshold for each communication link parameter aspart of the logic flow at 628. For example, based on the changes to thecommunication link parameters and the resulting user feedback, the userquality tolerance threshold may be determined indicating a user'stolerance for each characteristic. Stated differently, the user qualitytolerance threshold may comprise the minimum quality that a user willtolerate for each communication link parameter, below which it may bedesirable to handoff a the VoIP communication link between the hybridmobile device 124 and the call server 102 to another network such as amobile carrier network 110.

At 630 the logic flow may include the call server 102 and/or the hybridmobile device 124 creating a handoff profile based on the user qualitytolerance threshold of the communication parameters. For example, thehandoff profile may be unique to a hybrid mobile device 124, a user of adevice, or a user of an account or may be shared across any number ofdevices, users or accounts. The handoff profile may comprise thresholdlevels for the various communication link parameters such that when oneor more of the communication link parameters dips below its thresholdlevel, initiation of a handoff of the communication link from the VoIPnetwork to an alternate network may be commenced.

The call server 102 may forward a new handoff profile to the hybridmobile device 124 at 632 in the logic flow and at 634 the logic mayinclude updating the hybrid mobile device 124 with the new handoffprofile. For example, once the handoff profile is established, it may beforwarded, via the call server 102 for example, to the hybrid mobiledevice 124 from which the user feedback originated. That originatinghybrid mobile device 124 may use that handoff profile moving forward tomake network and/or communication link handoff decisions. In embodimentswhere the hybrid mobile device 124 re-calculated the handoff profile, itmay update the handoff profile itself. Other embodiments are describedand claimed.

FIG. 6C illustrates an example of a third logic flow. As shown in FIG.6C, the third logic flow includes a logic flow 640. Logic flow 640 maybe representative of some or all of the operations executed by one ormore logic, features, or devices described herein, such as any devices,systems, methods and/or techniques described above with references toFIGS. 1-5B for example. More particularly, logic flow 640 may beimplemented by CLH logic 340 of a mobile device 124 in some embodiments.In various embodiments, the logic flow 640 may be representative of someor all of the operations associated with a call server simulatingcommunication link parameters or simulating communication linkparameters without involving the call server 102 and soliciting feedbackon a hybrid mobile device 124 to establish or update a handoff profilevia a dedicated software application or program running on the hybridmobile device 124 without the need to establish a test call or an actualconnection to another device such as the call server 102. Otherembodiments are described and claimed.

In various embodiments, the logic flow at 642 may include a user openingan application executing on a hybrid mobile device 124 specifically togauge the user's tolerance to communication link parameters andcommunication link parameter changes. For example, the application(“app”) may comprise an application, software program or other logicstored on hybrid mobile device 124 and used for purposes of calibratinga handoff profile for the user and/or the hybrid mobile device 124.While described in terms of an application being opened by a user, theembodiments are not limited in this respect. In some embodiments, theapplication may be arranged to run automatically when a hybrid mobiledevice 124 is activated, when a hybrid mobile device 124 is powered onand/or whenever the hybrid mobile device 124 detects a new network. Theembodiments are not limited in this respect.

At 644 the logic flow may include the application simulating and varyingmultiple communication link parameters (e.g. packet loss, jitter,latency, etc.). For example, rather than establish a real communicationlink or a test communication link, the application may be operative toplay back an audio signal that varies in a manner that simulatesvariances in one or more communication link parameters. The user mayprovide feedback for each communication link parameter as part of thelogic flow at 646. For example, as the application simulates thevariations in the communication link parameters, the user may beinstructed to listen and to provide feedback when the audio signal isnot of an acceptable quality.

In some embodiments, the logic flow at 648 may include the applicationdetermining a user feedback tolerance threshold for each communicationlink parameter. As described above, the user feedback tolerancethreshold may be determined based on the user feedback and one or moreof the communication link parameters at the time of the user feedback toensure that a handoff is initiated when one or more of the communicationlink parameters drop below the threshold, resulting in potentially poorconnection quality.

At 650 the logic flow may include the application creating a handoffprofile based on the user quality tolerance threshold of thecommunication link parameters and at 652 the logic flow may include thehybrid mobile device 124 being updated with the new handoff profile. Forexample, once the handoff profile is established by the application, itmay be stored on the hybrid mobile device 124 containing and/orexecuting the application and on which the user feedback was received.The hybrid mobile device 124 may use that handoff profile moving forwardto make network and/or communication link handoff decisions. Otherembodiments are described and claimed.

FIG. 6D illustrates an example of a fourth logic flow. As shown in FIG.6D, the fourth logic flow includes a logic flow 660. Logic flow 660 maybe representative of some or all of the operations executed by one ormore logic, features, or devices described herein, such as any devices,systems, methods and/or techniques described above with references toFIGS. 1-5B for example. More particularly, logic flow 660 may beimplemented by CLH logic 340 of a portion of a call server 102 in someembodiments. Alternatively, a separate web-server may be stood up justfor this purpose. In various embodiments, the logic flow 660 may berepresentative of some or all of the operations associated with a callserver simulating communication link parameters or communication linkparameters being simulated without involving the call server 102 whereinfeedback is solicited via a website or web browser that is operative toact as a substitute for the hybrid mobile device 124 to establish orupdate a handoff profile without the need to establish a test call or anactual connection to a call server 102 and also without the need topossess or involve the hybrid mobile device 124. Other embodiments aredescribed and claimed.

In various embodiments, the logic flow at 662 may include a usernavigating to a website linked with a hybrid mobile device 124 servicespecifically to gauge the user's tolerance to communication linkparameters. For example, a website, web server or other server availablevia the Internet may be accessible by a user or a prospective user of ahybrid mobile device 124. This website may be operative to present oneor more communication link parameters and/or simulate a connection thatthe user may utilize for establishing communication connections with ahybrid mobile device 124. Other embodiments are described and claimed.

At 664 the logic flow may include the user providing authenticationinformation to link a session to a specific hybrid mobile deviceaccount. For example, a user may log in to the website to access anexisting account with a service provider or may be prompted to create anew account if they do not already have an account. In variousembodiments the logic flow may include the website simulating and/orvarying multiple communication link parameters (e.g. packet loss,jitter, latency, etc.) at 668. For example, and as recited above withrespect to logic flow 640, rather than establish a real communicationlink or a test communication link, the website may be operative to playback audio signals that vary in a manner that simulates variances in oneor more communication link parameters. The user may provide feedback foreach communication link parameter as part of the logic flow at 670. Forexample, as the website simulates the variations in the communicationlink parameters, the user may be instructed to listen and to providefeedback when the audio signal is not of an acceptable quality.

In various embodiments, at 672 the logic flow may include the websitedetermining a user feedback tolerance threshold for each communicationlink parameter, at 674 the logic flow may include the website creating ahandoff profile based on the user quality tolerance threshold ofcommunication link parameters, at 676 the logic flow includes thewebsite forwarding the handoff profile to a call server 102 and/or ahybrid mobile device 124 and at 678 the logic flow includes a hybridmobile device 124 being updated with the new handoff profile. The userfeedback tolerance threshold may be determined based on the userfeedback and one or more of the communication link parameters at thetime of the user feedback to ensure that a handoff is initiated for theuser of the associated account when one or more of the communicationlink parameters drop below the threshold, resulting in potentially poorconnection quality. In various embodiments, one the handoff profile isestablished by the website, it may be associated with a user accountbased on the authentication information. The call server 102 or hybridmobile device 124 may use that handoff profile moving forward to makenetwork and/or communication link handoff decisions for that user and/orthe handoff profile may be forwarded to a hybrid mobile device 124associated with the user's account and provisioned on that hybrid mobiledevice 124. Other embodiments are described and claimed.

FIG. 6E illustrates an example of a fifth logic flow. As shown in FIG.6E, the fifth logic flow includes a logic flow 680. Logic flow 680 maybe representative of some or all of the operations executed by one ormore logic, features, or devices described herein, such as any devices,systems, methods and/or techniques described above with references toFIGS. 1-5B for example. More particularly, logic flow 680 may beimplemented by CLH logic 340 of a call server 102 in some embodiments.In various embodiments, the logic flow 680 may be representative of someor all of the operations associated with obtaining and utilizing userfeedback from multiple users and/or multiple hybrid mobile devices 124to establish or update a community handoff profile. Other embodimentsare described and claimed.

At 682 the logic flow may include the call server 102 and/or web servercollecting communication link parameter tolerance thresholds formultiple users. For example, using any one or more of theabove-described methods, communication link parameter tolerancethresholds may be gathered for multiple users. The logic flow at 684 mayinclude the communication link parameter tolerance thresholds for themultiple users being processed to determine average tolerance thresholdsfor each communication link parameter. For example, the threshold foreach parameter (e.g. jitter, latency, etc.) may be averaged across anynumber of the received communication link parameter tolerancethresholds. In various embodiments, at 686 the logic flow may includeaveraging the tolerance thresholds for each communication link parameterto create a community default handoff profile. For example, thecommunity default handoff profile may comprise a combination ofpreferences for any number of users that are used to establish baselinethresholds for an entire community of users, rather than relying ondevice or user specific thresholds.

The logic flow at 688 may include the community default handoff profilebeing stored in a call server 102 and/or a web server associated withone or more user accounts. For example, once established the communitydefault handoff profile may be stored on a web server or call server 102used by the one or more devices to establish communication connections.In some embodiments, the logic flow at 690 may include the communitydefault handoff profile being provisioned on new hybrid mobile devices124 and/or sent to existing hybrid mobile devices 124. For example, asnew hybrid mobile devices 124 are added to or associated with the callserver 102, these hybrid mobile devices 124 may be provisioned with thecommunity default handoff profile. Similarly, existing hybrid mobiledevices 124 already associated with the call server may be updated withthe newly established or updated community default handoff profile.Other embodiments are described and claimed.

FIG. 7 illustrates an embodiment of a first storage medium. As shown inFIG. 7, the first storage medium includes a storage medium 700. Storagemedium 700 may comprise an article of manufacture. In some examples,storage medium 700 may include any non-transitory computer readablemedium or machine-readable medium, such as an optical, magnetic orsemiconductor storage. Storage medium 700 may store various types ofcomputer executable instructions, such as instructions to implement oneor more of logic flows 600, 620, 640, 660 and/or 680. Examples of acomputer readable or machine readable storage medium may include anytangible media capable of storing electronic data, including volatilememory or non-volatile memory, removable or non-removable memory,erasable or non-erasable memory, writeable or re-writeable memory, andso forth. Examples of computer executable instructions may include anysuitable type of code, such as source code, compiled code, interpretedcode, executable code, static code, dynamic code, object-oriented code,visual code, and the like. The examples are not limited in this context.

FIG. 8 illustrates an embodiment of a device 800. In some examples,device 800 may be configured or arranged for wireless communications ina wireless network. Device 800 may implement, for example, any of thedevices, apparatus and/or systems described herein such as mobile device124 for example. The logic circuit 870 may include physical circuits toperform operations described for apparatus 100. As shown in FIG. 8,device 800 may include a radio interface 810, baseband circuitry 820,and computing platform 830, although examples are not limited to thisconfiguration.

The device 800 may implement some or all of the structure and/oroperations for apparatus 100, storage medium 700 and/or logic circuit870 in a single computing entity, such as entirely within a singledevice. The embodiments are not limited in this context.

Radio interface 810 may include a component or combination of componentsadapted for transmitting and/or receiving single carrier ormulti-carrier modulated signals (e.g., including complementary codekeying (CCK) and/or orthogonal frequency division multiplexing (OFDM)symbols and/or single carrier frequency division multiplexing (SC-FDMsymbols) although the embodiments are not limited to any specificover-the-air interface or modulation scheme. Radio interface 810 mayinclude, for example, a receiver 812, a transmitter 816 and/or afrequency synthesizer 814. Radio interface 810 may include biascontrols, a crystal oscillator and/or one or more antennas 818-f. Inanother embodiment, radio interface 810 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

Baseband circuitry 820 may communicate with radio interface 810 toprocess receive and/or transmit signals and may include, for example, ananalog-to-digital converter 822 for down converting received signals, adigital-to-analog converter 824 for up converting signals fortransmission. Further, baseband circuitry 820 may include a baseband orphysical layer (PHY) processing circuit 826 for PHY link layerprocessing of respective receive/transmit signals. Baseband circuitry820 may include, for example, a processing circuit 828 for medium accesscontrol (MAC)/data link layer processing. Baseband circuitry 820 mayinclude a memory controller 832 for communicating with MAC processingcircuit 828 and/or a computing platform 830, for example, via one ormore interfaces 834.

In some embodiments, PHY processing circuit 826 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames (e.g., containing subframes). Alternatively or inaddition, MAC processing circuit 828 may share processing for certain ofthese functions or perform these processes independent of PHY processingcircuit 826. In some embodiments, MAC and PHY processing may beintegrated into a single circuit.

Computing platform 830 may provide computing functionality for device800. As shown, computing platform 830 may include a processing component840. In addition to, or alternatively of, baseband circuitry 820 ofdevice 800 may execute processing operations or logic for apparatus200/300, storage medium 800/900, and logic circuit 870 using theprocessing component 830. Processing component 840 (and/or PHY 826and/or MAC 828) may comprise various hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude devices, logic devices, components, processors, microprocessors,circuits, processor circuits (e.g., processor circuit 820), circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an example isimplemented using hardware elements and/or software elements may vary inaccordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a given example.

Computing platform 830 may further include other platform components850. Other platform components 850 include common computing elements,such as one or more processors, multi-core processors, co-processors,memory units, chipsets, controllers, peripherals, interfaces,oscillators, timing devices, video cards, audio cards, multimediainput/output (I/O) components (e.g., digital displays), power supplies,and so forth. Examples of memory units may include without limitationvarious types of computer readable and machine readable storage media inthe form of one or more higher speed memory units, such as read-onlymemory (ROM), random-access memory (RAM), dynamic RAM (DRAM),Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM(SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

Computing platform 830 may further include a network interface 860. Insome examples, network interface 860 may include logic and/or featuresto support network interfaces operated in compliance with one or morewireless broadband technologies such as those described in one or morestandards associated with IEEE 802.11 such as IEEE 802.11 ad.

Device 800 may be, for example, user equipment, a computer, a personalcomputer (PC), a desktop computer, a laptop computer, a notebookcomputer, a netbook computer, a tablet computer, an ultrabook computer,a smart phone, embedded electronics, a gaming console, a server, aserver array or server farm, a web server, a network server, an Internetserver, a work station, a mini-computer, a main frame computer, asupercomputer, a network appliance, a web appliance, a distributedcomputing system, multiprocessor systems, processor-based systems, orcombination thereof. Accordingly, functions and/or specificconfigurations of device 800 described herein, may be included oromitted in various embodiments of device 800, as suitably desired. Insome embodiments, device 800 may be configured to be compatible withprotocols and frequencies associated with IEEE 802.11 Standards forWLANs and/or for wireless docking, although the examples are not limitedin this respect.

Embodiments of device 800 may be implemented using single input singleoutput (SISO) antenna architectures. However, certain implementationsmay include multiple antennas (e.g., antennas 818-f) for transmissionand/or reception using adaptive antenna techniques for beamforming orspatial division multiple access (SDMA) and/or using multiple inputmultiple output (MIMO) communication techniques.

The components and features of device 800 may be implemented using anycombination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of device 800 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic” or “circuit.”

It should be appreciated that the exemplary device 800 shown in theblock diagram of FIG. 8 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would be necessarily bedivided, omitted, or included in embodiments.

Some examples may be described using the expression “in one example” or“an example” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one example. The appearances ofthe phrase “in one example” in various places in the specification arenot necessarily all referring to the same example.

Some examples may be described using the expression “coupled”,“connected”, or “capable of being coupled” along with their derivatives.These terms are not necessarily intended as synonyms for each other. Forexample, descriptions using the terms “connected” and/or “coupled” mayindicate that two or more elements are in direct physical or electricalcontact with each other. The term “coupled,” however, may also mean thattwo or more elements are not in direct contact with each other, but yetstill co-operate or interact with each other.

It is emphasized that the Abstract of the Disclosure is provided tocomply with 37 C.F.R. Section 1.72(b), requiring an abstract that willallow the reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single example for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimed examplesrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter lies in lessthan all features of a single disclosed example. Thus the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separate example. In the appended claims,the terms “including” and “in which” are used as the plain-Englishequivalents of the respective terms “comprising” and “wherein,”respectively. Moreover, the terms “first,” “second,” “third,” and soforth, are used merely as labels, and are not intended to imposenumerical requirements on their objects.

What is claimed is:
 1. At least one non-transitory machine-readablemedium comprising a set of instructions that in response to beingexecuted on a computing device cause the computing device to: establisha test voice call between a hybrid mobile device and a call server overa Voice-over Internet Protocol (VoIP) network; simulate values for oneor more VoIP communication link parameters pertaining to a perceivedquality of the test voice call; receive user feedback during the testvoice call between the hybrid mobile device and the call server, theuser feedback, as received from a user of the hybrid mobile device,correlating VoIP communication link parameter values associated withgood perceived quality of the test voice call and VoIP communicationlink parameter values associated with bad perceived quality of the testvoice call; determine call quality threshold values for each of the oneor more VoIP communication link parameters based on the received userfeedback, the call quality threshold values separating said goodperceived quality from said bad perceived quality; and create a handoffprofile unique to the hybrid mobile device based on the call qualitythreshold values, the handoff profile establishing criteria for handingoff a VoIP communication link to a communication link over an alternatenetwork or an alternate access point on subsequent voice calls made orreceived by the hybrid mobile device.
 2. The at least one non-transitorymachine-readable medium of claim 1, the handoff profile comprising callquality threshold values for each of the VoIP communication linkparameters.
 3. The at least one non-transitory machine-readable mediumof claim 1, the VoIP communication link parameters comprising one ormore of received signal strength, jitter, latency, packet loss, linkspeed, and link throughput.
 4. The at least one non-transitorymachine-readable medium of claim 1, comprising instructions that inresponse to being executed on the computing device cause the computingdevice to: during a subsequent voice call, initiate a handoff of a VoIPcommunication link to an alternate communication link using thealternate network or the alternate access point when at least one of theVoIP communication link parameter values crosses, from good to bad, itscall quality threshold value in the handoff profile.
 5. The at least onenon-transitory machine-readable medium of claim 1, comprisinginstructions that in response to being executed on the computing devicecause the computing device to: during a subsequent voice call, initiatea handoff of the VoIP communication link to an alternate communicationlink using the alternate network or the alternate access point when twoor more of the VoIP communication link parameter values are within apre-determined range of their corresponding call quality thresholdvalues in the handoff profile.
 6. The at least one non-transitorymachine-readable medium of claim 1, comprising instructions that inresponse to being executed on the computing device cause the computingdevice to: update, in the call server, the handoff profile of the hybridmobile device based on the most recent user feedback data.
 7. The atleast one non-transitory machine-readable medium of claim 1, comprisinginstructions that in response to being executed on the computing devicecause the computing device to: update, in the hybrid mobile device, thehandoff profile of the hybrid mobile device based on the most recentuser feedback data.
 8. The at least one non-transitory machine-readablemedium of claim 1, comprising instructions that in response to beingexecuted on the computing device cause the computing device to:separately vary each of the one or more VoIP communication linkparameters pertaining to the perceived quality of the test voice calluntil negative user feedback indicative of bad voice call quality isreceived.
 9. The at least one non-transitory machine-readable medium ofclaim 1, comprising instructions that in response to being executed onthe computing device cause the computing device to: vary multiple of theone or more VoIP communication link parameters pertaining to theperceived quality of the test voice call simultaneously until negativeuser feedback indicative of bad voice call quality is received.
 10. Theat least one non-transitory machine-readable medium of claim 1, the userfeedback comprising one or more of activation of one or moreinput/output (I/O) devices of the hybrid mobile device, interaction witha graphical user interface (GUI) element displayed on a touch sensitivedisplay of the hybrid mobile device, or activation of one or moresensors of the hybrid mobile device.
 11. The at least one non-transitorymachine-readable medium of claim 1, the alternate network comprising amobile network.
 12. An apparatus, comprising: a processor component;communication link handoff (CLH) logic to be executed by the processorcomponent to: establish a test voice call between a hybrid mobile deviceand a call server over a Voice-over Internet Protocol (VoIP) network;simulate values for one or more VoIP communication link parameterspertaining to a perceived quality of the test voice call; receive userfeedback during the test voice call between the hybrid mobile device andthe call server, the user feedback, as received from a user of thehybrid mobile device, correlating VoIP communication link parametervalues associated with good perceived quality of the test voice call andVoIP communication link parameter values associated with bad perceivedquality of the test voice call; determine call quality threshold valuesfor each of the one or more VoIP communication link parameters based onthe received user feedback, the call quality threshold values separatingsaid good perceived quality from said bad perceived quality; and createa handoff profile unique to the hybrid mobile device based on the callquality threshold values, the handoff profile establishing criteria forhanding off a VoIP communication link to a communication link over analternate network or an alternate access point on subsequent voice callsmade or received by the hybrid mobile device.
 13. The apparatus of claim12, the handoff profile comprising call quality threshold values foreach of the VoIP communication link parameters.
 14. The apparatus ofclaim 12, the VoIP communication link parameters comprising one or moreof received signal strength, jitter, latency, packet loss, link speed,and link throughput.
 15. The apparatus of claim 12, the CLH logicexecuted by the processor component further to: during a subsequentvoice call, initiate a handoff of a VoIP communication link to analternate communication link using the alternate network or thealternate access point when at least one VoIP communication linkparameter values crosses, from good to bad, its call quality thresholdvalue in the handoff profile.
 16. The apparatus of claim 12, the CLHlogic executed by the processor component further to: during asubsequent voice call, initiate a handoff of the VoIP communication linkto an alternate communication link using the alternate network or thealternate access point when two or more of the VoIP communication linkparameter values are within a pre-determined range of theircorresponding call quality threshold values in the handoff profile. 17.The apparatus of claim 12, the CLH logic executed by the processorcomponent further to: update, in the call server, the handoff profile ofthe hybrid mobile device based on the most recent user feedback data.18. The apparatus of claim 12, the CLH logic executed by the processorcomponent further to: update, in the hybrid mobile device, the handoffprofile of the hybrid mobile device based on the most recent userfeedback data.
 19. The apparatus of claim 12, the CLH logic executed bythe processor component further to: separately vary each of the one ormore VoIP communication link parameters pertaining to the perceivedquality of the test voice call until negative user feedback indicativeof bad voice call quality is received.
 20. The apparatus of claim 12,the CLH logic executed by the processor component further to: varymultiple of the one or more VoIP communication link parameterspertaining to the perceived quality of the test voice callsimultaneously until negative user feedback indicative of bad voice callquality is received.
 21. The apparatus of claim 12, the user feedbackcomprising one or more of activation of one or more input/output (I/O)devices of the hybrid mobile device, interaction with a graphical userinterface (GUI) element displayed on a touch sensitive display of thehybrid mobile device, or activation of one or more sensors of the hybridmobile device.
 22. The apparatus of claim 12, the alternate networkcomprising a mobile network.